Lets take them one at a time

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

One of the resources are not available for reservation. The resource can be found while booking if searched by using "find time for a specific room", but not if searched by "find room at a specific time".

Ok, so you are direct booking and not getting the same results either way. These 2 searches are performed slightly differently. The "specific room" search builds a list of R&R names in the dB and then presents it to you to pick from. Once you pick, it searches for busytime for that room or resource only and returns it to you. The "specific time" search grabs all the names in the R&R dB and then uses all of them in one big busytime search. Those that are available at the time you specify are returned to you to pick from.

It could be an issue with your ($Resources) view being bad. If that is the case then a simple load updall -R myRnRDB.nsf console command on your R&R server should fix it up.

Can you search for that name from a Calendar w/o any problems? If you cannot then you need see what the error is that is being returned to the client and we and go from there. The easy way to find out the error is to simply manually specify the room on a meeting invite and then click in the gray "No Info" part of the schedule UI grid on the "Find Available Times" tab next to the name. IF there is an error, it will be displayed in the status bar. If there is none, nothing will show. Post the error you get here and we can continue from there.

Also if we try to book the resource from mail calendar, then it's available if we use the "Resources" link but not if we use the "Find REsources" button.

That is due to the difference between the options you used.

Find Resources actually searches busytime for entries that are available and lists them for you to pick from. Only entries that are available (or do not have an error of some kind) will be listed to you.
Resources does not actually search busytime to see if the selected name is busy or not. It merely allows you to pick the name you want from the list of all possible names and then you are expected to check to make sure its available in the UI grid. We did add a "Is the requested room still available?" check to the mail template in 8.5x to catch cases like this and warn you with a dialog in case it no longer is or you simply did not check before trying to send the invite out.

It is sounding more and more like there is no entry for that resource in the busytime system so that is probably where the investigation should focus. As noted above, if you can get an error message we can progress further on this issue.

There was an issue like this that was fixed in 8.51 which dealt with the template not correctly making some item changes on the room doc when you made a restriction change.

Please make sure your template matches your code version and is not an older template on the newer installation. For reference, the SPR that addresses this is UTOO7G8F5Y. Oh yes, do not forget to reenable the 4 "system" agents in the R&R dB once you update your design.

When dealing with R&R, you should be sending commands to the RnRMgr task, not Sched. Sched is now only for users and RnRMgr is only for R&R. Some commands will work on either task for either type but not all will so you should get into the habit of using the right task. For example tell rnrmgr show Bruce Kahn/IBM will work exactly like tell sched show Bruce Kahn/IBM but other commands like check or validate will not.

There is a known issue where the R&R template will create a profile doc (aka room doc) that has no $BusyName on it. It does this the first time the database is opened initially (because there is database scripts that try to get some info when the database is opened and the side effect is a 'runt' profile is created. This is not a problem that affects R&R working and is totally safe to ignore.

Try using the tell rnrmgr list command with the full room hierarchical name and see what is shows. Does it show the room settings or does it show an error? You should also try the validate command with RnRMgr and see what it says works or fails.

Bruce
IBM

Feedback response number BKAN93XT8Q created by ~Lex Nontookonynivu on 01/14/2013